Task: Request Propagation
Propagation Requests (PR) are opened through this activity.
Disciplines: Change Management
Purpose
Propagation Requests (PR) are opened through this activity.
Relationships
RolesPrimary Performer: Additional Performers:
Outputs
    Main Description

    Propagation Request plays an important role in this process, being the main gateway for changes to be propagated from Core Asset Development to Product Development and vice-versa.

    Whenever a Core Asset or Product Release is published (Or in any other time) a propagation request can be opened to update the other area. For example, if a new core asset release is published, a new propagation request can be opened for the product that uses that core asset to update the version it uses.

    This process of propagation starts with the PR. The PR must contain all important and detailed information about the propagation being requested in order for the CCB group make their analysis of the PR and then approve it for the propagation of that change/release.

    Steps
    Define Change Set targeted to propagation

    In this step the requester has to list the changeset that will be propagated [ e.g. set of CRs (a release), or a single CR ]

    Every PR has to be related with one or more CRs.

    Select Propagation Type in the Change Control Tool

    Propagation Requests can be of different types [Kobra]:
    - Feedback: From the PD -> CAD
    - Rebase: From the CAD -> CAD

    The other possibility is the internal propagation:
    - Internal Propagation: PD -> PD      or     CAD -> CAD
    Revise Form and Submit
    Before submitting the PR make sure that all informations are consistent and clear.
    Key Considerations
    Propagation Request plays an important role in this process, being the main gateway for changes to be propagated from Core Asset Development to Product Development and vice-versa. The PR is always related to a CR or a set of CRs.